Vendor token generator

ABSTRACT

A method for generating tokens for use in an email-based e-commerce transaction between third party vendor and a customer that is facilitated by a payment server is disclosed. The method may comprise generating a token for use with an email checkout, wherein the token comprises a customer name, and customer email address. The processor may generate an email message for at least one recipient, the email message including a mailto hyperlink including the token, wherein the mailto hyperlink generates an email response message addressed to the payment server including the token. The method may comprise receiving a notification from the payment server indicating that the at least one recipient that the email response message was successfully received by the payment server and the email-based e-commerce transaction is successful.

CROSS REFERENCE TO RELATED APPLICATION

This application is a Continuation of U.S. patent application Ser. No.14/216,227 filed Mar. 17, 2014, which claims the benefit of U.S.provisional Application No. 61/794,675, filed on Mar. 15, 2013, theentire contents of which are incorporated by reference as if fully setforth.

FIELD OF INVENTION

The present invention is related to electronic payment systems.

BACKGROUND

Vendors wishing to adopt an email-based payment method may need tointegrate their own system with a third party system to use the emailpayment process. An email payment system may demand a close integrationbetween the vendor and the e-commerce system. This setup may be timeconsuming and cumbersome for the vendor.

In designing an email payment system, problems may arise when the userbase begins to scale the system to accommodate more users. Thecommunication between the gateway and the vendor may be considerabledepending on the size of the customer base and the array of offers.Larger numbers may use more bandwidth. Many online businesses' profitsare dependent on the ability to scale their customer base. Any systemthat enters the marketplace must take into account large numbers ofusers. A system that would require the use of less bandwidth would beadvantageous.

Online security is a concern for any vendor. Additionally, there areoften security concerns since these third party systems are not locatedon the vendor's system. When adopting new systems many vendors prefersystems that allow them autonomy. Limiting the amount of communicationbetween systems that may be communicating encrypted data over publicnetworks reduces potential interference from outside parties. A processintegrated directly in the vendor's system may reduce exposure.

Email-based payment systems contend with customers that are morefamiliar with web-based payment systems. Consumers expect to visit a URLto check out of merchandise. A two-click web URL checkout may be adesirable service for a vendor to provide to a client. Theimplementation of a tool that may generate tokens for web andemail-based checkout may be desirable.

SUMMARY

As described in greater detail herein, the system is configured toprovide vendors autonomy in generating tokens for both email and URLcheckout. A token generator may be integrated directly in the vendor'ssystem and may reduce communication with the email payment gateway. Thisconfiguration allows the vendor to produce tokens for email-basedpayments as well as two-click web-based checkout tokens. The tokengenerator allows vendors to include secure tokens in advertising emails.The vendor server sends emails with tokens to customers that areregistered to receive the email-based payment system. The emails containhyperlinks that correspond to offers from the vendor. When the mailtohyperlink is selected, the new email contains a token that holdsidentifiers of the associated offer and purchaser. That email may thenbe sent to the email payment gateway. The system receives the email anddecodes the contents of the email and processes the transaction. Acorresponding offer may be generated for a two-click web transactionbased on the token generator.

A method for generating tokens for use in an email-based e-commercetransaction between third party vendor and a customer that isfacilitated by a payment server is disclosed. The method may comprisegenerating a token for use with an email checkout, wherein the tokencomprises a customer name, and customer email address. The processor maygenerate an email message for at least one recipient, the email messageincluding a mailto hyperlink including the token, wherein the mailtohyperlink generates an email response message addressed to the paymentserver including the token. The method may comprise receiving anotification from the payment server indicating that the at least onerecipient that the email response message was successfully received bythe payment server and the email-based e-commerce transaction issuccessful.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description,given by way of example in conjunction with the accompanying drawingswherein:

FIG. 1 shows an example system that may be used for a vendor tokengenerator that may be used in e-commerce transactions;

FIG. 2 shows another example of a system for a vendor token generatorfor email and web-based checkout;

FIG. 3 shows a transactional diagram for a method for token generation;

FIG. 4 is a flow diagram for a method of token generation usingweb-based steps;

FIG. 5 shows a an example of a website token structure;

FIG. 6 shows an example of a web page for an URL Interface for webcheckout; and

FIG. 7 shows a transactional diagram for a method for generating a tokenwith a website.

DETAILED DESCRIPTION

When used herein, the term “token” may refer a sequence of byte data orstring or file used to authenticate a transaction. A token may be one ormultiple encrypted strings, files, passwords, cyphers or other datawhich may contain information used to perform or authenticate atransaction when sent to payment servers. These tokens may be encryptedusing a public-private key encryption system. The vendor or a party withknowledge of the vendor's private key may generate an encrypted token.Alternatively, a payment system or e-commerce site may generate thistoken on behalf of the vendor.

When used herein, the term “user agent” may refer to software and/orhardware that are acting on behalf of a user.

Disclosed herein are processor-executable methods, computing systems,and related technologies for a vendor token generator for e-commercetransactions. The system and method may use an email server/account tocomplete checkout of any type of product (e.g.,items/services/events/donations) for a transfer of funds from a customerto a vendor (e.g. retail site, charity, political organization or othervendor.) While the technologies described herein are described usingemail as an example, they may also be applicable to similarcommunication mediums, such as SMS and MMS communication channels.

FIG. 1 shows an example system 100 that may be used for vendor tokengeneration that may be used in e-commerce transactions. The examplesystem 100 includes a customer device 150, a vendor server 120, apayment server 140, and a banking server 160 that may communicate overone or more wired and/or wireless communication networks 110. The wiredor wireless communication networks 110 may be public, private or acombination of public or private networks.

The customer device 150 may be, for example, a cellular phone, asmartphone, a desktop computer, a laptop computer, a tablet computer, orany other appropriate computing device. The customer device 150 includesa processor 151, memory 152, a communications unit 153, a display unit154 and web browser unit 155, which may communicate data to/from the webserver module(s) in the vendor server 120 and payment server 140. Theweb browser unit 155 may include and/or communicate with one or moresub-modules that perform functionality such as rendering HTML (includingbut not limited to HTML5), rendering raster and/or vector graphics,executing JAVASCRIPT, and/or rendering multimedia content.

Alternatively or additionally, the web browser unit 155 may implementRich Internet Application (RIA) and/or multimedia technologies such asADOBE FLASH and/or other technologies compatible with Internet basedcommunications. The web browser unit 155 may implement RIA and/ormultimedia technologies using one or web browser plug-in modules (e.g.,ADOBE FLASH), and/or using one or more sub-modules within the webbrowser unit 155 itself. The web browser unit 155 may display data onone or more display devices (not depicted) that are included in, orconnected to, the customer device 150, such as a liquid crystal display(LCD) display or monitor. The customer device 150 may receive input fromthe user of the customer device 150 from input devices (not depicted)that are included in, or connected to, the customer device 150, such asa keyboard, a mouse, a microphone or a touch screen, and provide datathat indicates the input to the web browser unit 155.

The vendor server 120 may include an HTTP server module 121, a tokengenerator 122, a button generator 123, a processor 124, memory 125, apayment gateway 126 and a communications unit 127.

The HTTP server module 121 provides a website that may be accessed by acustomer device 150. The HTTP server module 121 may implement the HTTPprotocol, and may communicate Hypertext Markup Language (HTML) pages andrelated data from the website to/from the customer device 150 usingHTTP. The vendor server 120 may be connected to one or more private orpublic networks (such as the Internet), via which the HTTP server module121 communicates with devices such as the customer device 150. The HTTPserver module 121 may generate one or more web pages and may communicatethe web pages to the customer device 150, and may receive responsiveinformation from the customer device 150.

The HTTP server module 121 may be, for example, an NGINX server, anAPACHE HTTP server, a SUN-ONE Web Server, a MICROSOFT INTERNETInformation Services (IIS) server, and/or may be based on any otherappropriate HTTP server technology. The vendor server 120 may alsoinclude one or more additional components or modules (not depicted),such as one or more load balancers, firewall devices, routers, switches,and devices that handle power backup and data redundancy.

The payment gateway 126 may be a proprietary service that service thatdirectly connects with the payment processors, such as banking server160 to handle the credit card data, and authorize credit card payments.

The token generator 122 may generate tokens for use in e-commercetransactions. Tokens may be encrypted strings which contain informationto perform a transaction when sent to the payment server(s) 140. A tokenmay be one or multiple encrypted strings, files, passwords, cyphers orother data which may contain information used to perform or authenticatea transaction. A token may include one or more of the followingparameters or other parameters not listed below:

-   -   a) Private-key: The private key provided by the payment server        140.    -   b) Public-key: Payment server's 140 public key, provided by the        payment server 140.    -   c) Partner-id: The partner ID given provided by the payment        server.    -   d) Environment: The environment the vendor wants to generate        buttons for. This distinguishes whether the token is being used        in a testing environment or in the live environment (and running        real transactions).    -   e) Config: The path to a configuration file in yml format. This        may hold a default set of information, e.g., private_key,        public_key, partner_id, and other information—so they don't have        to be entered separately each time a token is generated. The        config field may also contain information specific to an offer        (e.g. dollar amount) or a customer (e.g. card token) if multiple        tokens are being generated with similar components.    -   f) Type: The type of token to generate (site, email, universal).        There are multiple types of tokens that a token generator may        generate and decode. For example, site tokens may be used for        website transactions, email tokens for two-click email payments,        and universal tokens for email validations.    -   g) Card: The card token associated with the recipient of this        token. When a customer is registered with the payment server        140, the vendor receives a credit card token—a unique identifier        that references the specific card associated with that customer        and vendor. When the vendor is generating a token to submit to        payment server 140, they may include the card token as a        customer identifier.    -   h) Email: The email associated with the receipt of this token.    -   i) URL: The Signup URL the recipient should go to if customer        does not have payment information registered with payment server        140.    -   j) Amount: The amount a user should be charged for the        transaction the token is generated for.    -   k) User-data: Data to pass back as a reference. This data may        include custom data that the vendor may want to pass through the        payment server 140 and receive back when a transaction has        completed. It may include an item reference number or SKU,        customer address, or any other piece of data that is not        required by payment server 140 to complete a transaction, but        that the vendor wants associated with that transaction.    -   l) Expires: Expiration date for token, integer value of seconds        since epoch.    -   m) Header-user-agent: The HTTP_USER_AGENT from the request        header. HTTP headers are sent as part of a request from a        customer's web browser unit 155 for a piece of information.        These headers define the parameters that the web browser unit        155 is expecting to get back. The user-agent is the identifier        of the software that is submitting the request—typically the        identifier of the web browser unit 155 that is requesting the        content.    -   n) Header-accept-language: The HTTP_ACCEPT_LANGUAGE from the        request header. The accept-language is the acceptable language        for the response—e.g. the language in which the web browser unit        155 is requesting the content be sent back.    -   o) Header-accept-charset: The HTTP_ACCEPT_CHARSET from the        request header. The accept-charset is the character sets that        are acceptable for the response—e.g. the character set in which        the web browser unit 155 is requesting the content be sent back.    -   p) IP-address: The IP address of the token recipient.

The system 100 is designed to allow the vendor flexibility to offerdeals for a limited time or number or responsive to available inventory.For example, the token may be configured to expire by default after twoweeks, or any predetermined time, or never expire. The vendor server 120may be configured to extend or shorten the expiration time of aparticular offer associated with a token without resenting an email orgenerating a new token. Also, the vendor server 120 may send emailupdates for an offer associated with a token. This may be predetermined,or may be later set, depending upon demand by customers. Additionally,the vendor server 120 may generate groups of token values that mayautomatically invalidate members of the group when one token isprocessed. This is useful when sending out multiple tokens via email toa single customer or when sending out tokens to multiple customers, butwhen the vendor wants only one or a predetermined number of tokens to beprocessed. Therefore, when these tokens are used, the other tokens areinvalidated, effectively rescinding the offered deal. The vendor server120 may further be configured to send email notifications that thepreviously submitted token is now invalid.

The button generator 123 may create cross-client and cross-browsercompatible buttons for email checkouts. In one embodiment, the buttongenerator 123 may include the token generator 122 to automaticallygenerate an associated token for each button that is created.

A button and an associated token, generated by the button generator 123and/or the token generator 122 may be embedded on a web page created bythe HTTP server module 121.

The memory 125 may be configured to store information associated withe-commerce transactions. This may include inventory information,information used to generate web pages, customer information, and othere-commerce data.

The payment server 140 may include an HTTP server module 141, a tokengenerator 142, a processor 143, memory 144, payment gateway 145 and acommunications unit 146. While only one vendor server 120 is showncommunicating with the payment server 140, this is shown as an exampleonly. Payment server 140 may communicate with multiple vendor servers120. A customer, wishing to use the services of the payment server 140,may register his/her email address and payment information with thepayment server 140. Similarly, vendors may register with the paymentserver 140. The payment server 140 may provide the vendor server 120with a public key and private key to be used in token transaction inaccordance with the methods described herein. When a transaction isattempted, the payment server 140 decodes the token, authenticates thesender of the email, and may process the transaction. While the paymentserver 140 is depicted as a separate entity in FIG. 1, this is shown asan example only. The payment server 140 may be controlled and/orco-located with the vendor server 120, the banking server 160.

The banking server 160 may be controlled by a third party system bank.The payment server 140 may communicate with the banking server 160 toverify that the customer has adequate funds or credit for the requestedpurchase. For example, the banking server 160 may be a controlled byVISA, AMERICAN EXPRESS, MASTERCARD or any other bank or banking orfinancial network that a customer may use for online payment. Thebanking server 160 may be a server for virtual currencies, such asBITCOIN, etc.

FIG. 2 shows another example of a system for a vendor token generatorfor email and web-based checkout. As shown in FIG. 2, the example systemmay include a vendor server 120, a customer device 150, an e-commercesystem 170 and a payment processing system 180. The architecture shownin FIG. 2 enables vendors to generate two-click tokens within their ownvendor server 120, without requiring communication with the e-commercesystem 170 at the time the tokens are created. As shown in FIG. 2, theexample vendor server 120 may include token generator 122, a vendoremail server 128 and vendor website 129. The example customer device 150may comprise a two-click web checkout unit 155, an email client offeremail module 156 an email client sign up email module 157 and webbrowser signup module 158. The e-commerce system 170 may comprise atoken decoding unit 171, interface unit 172, a database module 176, anorder execution unit 173, a message processing unit 174 and an accountmanagement unit 175. The two-click web checkout unit 155 may be anapplication or API or software based module enabling the customer device150 to participate in a two-click web checkout. The email client offeremail module 156 and the email client sign up email module 157 may beintegrated with an email client or web client associated with thecustomer device 150. The web browser signup module 158 may be configuredto facilitate the signing a customer up with the e-commerce system 170as well as signing the customer in. This may facilitate the ability ofthe customer device 150 to respond to offers (e.g. without requiringmanually signing in each time).

Regarding the e-commerce system 170, the token decoding unit 171 may beconfigured to decode tokens. The interface unit 172 may be configured tointerface with the vendor server 120, the payment processing system 180,and one or more customer devices 150. The message processing unit 174may be configured to process received email messages and to generateemail messages. The order execution unit may be configured to executee-commerce transactions. The account management unit 175 may beconfigured to manage accounts of a plurality of members (both vendorsand customers) associated with the e-commerce system 170.

There may be multiple methods and types of two-click tokens that may begenerated. As shown in the example of FIG. 2, there are two types shown.The vendor server 120 may generate a first type of token may for usewith email checkout and/or a second type of token for URL checkout. Theorder in which the tokens are generated may be based on the time atwhich a vendor requests a token. The system is configured to use asecure and backwards compatible process for facilitation during theintegration process. The methods and apparatus described herein mayprovide the vendor server 120 with improved security embedding morefunctionality in the vendor server 120. The methods described herein mayreduce bandwidth by streamlining communications with the e-commercesystem 170.

The vendor server 120 may generate an email offer that may be processedby the vendor email server 128. The token generator 122 may create thetoken to provide a purchase opportunity. In one embodiment, the tokenmay be generated without requiring contact with the e-commerce system's170 API. In another embodiment, the token may be created with somecontact with the e-commerce system 170.

Token generation by the vendor server 120 may involve a public keycryptography solution, which currently may use the following technologycomponents: encryption, using an XSalsa20 stream cipher; authenticationusing Polyl305 MAC; and/or public keys using Curve25519 high-speedelliptic curve cryptography. This above algorithms are used merely as anexample to illustrate the user of public key cryptography, and not meantto be limiting to those specific algorithms.

To enable the vendor server 120 to create a token, the token generator122 may comprise a token generation library is installed in the vendorserver 120. The token generator 122 may comprise a custom library thatmeets token protocol formatting requirements determined by thee-commerce system 170.

The vendor server 120 may be configured with keys provided by thee-commerce system 170. The vendor server 120 receives a unique privateand public key associated with the vendor, and a public key that thee-commerce system 170 uses for multiple partners. The vendor server 120may generate a token with their unique key, and provide the e-commercesystem's 170 public key as the intended target for messages.

The vendor server 120 inputs the required parameters for the specifiedtoken type into the token generator 122 and receives back the encryptedtoken containing some combination of the following information that thevendor may input:

-   -   a. token type;    -   b. card token (associated with the recipient of this token);    -   c. email address for recipient (user that may be initiating a        payment via two-click);    -   d. amount of the transaction (numeric value);    -   e. a unique partner id given to the partner (similar to the UUID        but an additional column of a different type);    -   f. signup URL (where the recipient is directed if their payment        information is not on file);    -   g. expiration date (after this time the token is no longer        considered valid)    -   h. group (tokens with a group equal to this value may not be        considered valid after the execution of a single member);    -   i. user data (data the vendor wants returned as a reference);        and/or    -   j. computer/browser identifiers (identifies user for security        purposes).

The e-commerce system's 170 message processing unit 174 receives anemail containing an encoded token (e.g. Base64), the e-commerce system170 decrypts the key into the above information, confirms the key'svalidity, ensures that the vendor server 120 is authorized to generatetokens, and processes a payment for the user with the given emailaddress. In another example, the vendor server 120 may pass a memberidentifier instead of an email address, which may specify a specificcredit card or billing option to charge.

If a keyset is compromised, the e-commerce system 170 may be configuredto disable the compromised keyset and generate another. If a vendor keyis compromised, the e-commerce system 170 may simply reject theencrypted transaction tokens after revoking the signing keys. If thee-commerce system 170 private key is compromised, the e-commerce system170 may be configured to transmit a key update to users of thee-commerce system 170 and revoke incoming transactions prior to the dateof revocation.

The e-commerce system 170 may be configured to store a checksum of atoken after it has been used, and to prevent the same from being usedmore than once. The e-commerce system 170 may further be configured tostore a group reference number for a used token, and prevent the groupreference number from being used more than a predetermined number oftimes. In one embodiment, the e-commerce system 170 may not store keysprior to their usage, which may reduce the need for the database module176 to store all tokens at the time of their creation.

The token generator 122 may comprise a Ruby library that may allow thevendor server 120 to generate tokens upon receiving credentialsgenerated by the e-commerce system 170.

The e-commerce system 170 may include an off-site library-based tokengeneration system that may be configured to permit an automaticauthenticated execution of a transaction via a web interface. A vendorserver 120 that has its own private key and public key and thee-commerce system 170 public key may generate a token authorizing atransaction on the part of a customer. The customer device 150 or vendorserver 120 may deliver this payload via email or another type ofelectronic messaging. The e-commerce system 170 may further comprise anemail processing system that may be configured to verify an emailaddress associated with the sender of an email. This may permit thepayment server 140 to verify that the payload was indicated for use bythe recipient (since the email is included in the decrypted payloadmessage). To accommodate the processing of web-based checkout, thee-commerce system 170 may be configured to use a verification using theincoming IP address and browser details to assist in decoding certaintoken types.

In another embodiment, the e-commerce system 170 may performauthentication of a payload based on a combination of browseridentification settings, an Internet connectivity address, and partnerkey generation.

FIG. 3 shows a transactional diagram for a method 300 for tokengeneration. As shown in FIG. 3, a vendor may post an offer on vendorwebsite 129 or generate an email using the vendor email server 128(steps 302 and 306). Both may rely on the token generator 122 togenerate a token (step 304). The token generator 122 as described abovemay create different types of tokens depending on the campaign. In thecase of an email campaign, the vendor email server 128 may transmit thegenerated token as a part of an email message (step 308). Similarly, thecustomer may checkout the transaction from either the URL or an email.The system may be configured to allow a user to select multiple types ofintended targets for a campaign. For example, when generating an offer,a user may select email recipients, a web page, a social media account,mobile phone numbers etc. The system may generate specific types oftokens for each type of intended recipient (e.g. SMS, email, web pageetc.) A customer may checkout from the URL associated with the vendorwebsite 129 or send a response email with the token embedded (steps 310and 312), which then allows the e-commerce system 170 to decode thetoken and process the transaction. If the transaction is successful, thee-commerce system may then send a notice of successful transaction tothe vendor email server 128 which may send an email to the customerdevice 150.

FIG. 4 is a flow diagram for a method 400 of token generation usingweb-based steps. A customer device 150 may access a web page associatedwith a vendor. While accessing a web page, a browser client or appassociated with the customer device 150 may request a page from thevendor server 120 (step 402). For example, the customer may browse to awith a price total offer on it. This web page may comprise a series ofprices presented for one or more products and one or more quantities theweb page may be for a checkout after a total is presented to thecustomer. In response to this request, the vendor server 120 maygenerate a token for an offer (step 404). This token may comprise an IPaddress and browser identifiers. The customer device 150 may be used toselect an offer presented on the web page, which transmits a purchaserequest to the payment server 140 (step 406). This payment request maybe transmitted directly from the customer device 150 or from the vendorserver 120. The payment request may include an IP address and browseridentifiers associated with the customer device 150 and/or the user ofthe customer device 150. The payment request is received by the paymentserver 140, which decrypts the token, and authenticates the IP addressand browser identifiers sent by the browser client (step 408). If thetoken, IP address and browser identifiers are authenticated, the paymentserver 140 may complete the transaction.

FIG. 5 shows an example of a structure for a website token 500. As shownin FIG. 5, element 502 may represent information that a vendor mayrequest to be in a token. This may be customized as described above. Thewebsite token may comprise a card token 504, a user IP address 506, andbrowser identifiers 508. These elements are shown only as an example, asa website token may contain different elements to authenticate atransaction as described above.

FIG. 6 shows example web page 600 for a URL interface web checkout thatmay be displayed by the web browser unit 155 of the customer device 150.The web page 600 may include display elements which allow the user ofthe customer device 150 to complete e-commerce transactions from avendor using one or more emails. The web page 600 may be included in aweb browser window that is displayed and managed by the web browser unit155. The web page 600 may include data received by the web browser unit155 from the vendor server 120 and/or the payment server 140. As shownin FIG. 6, the web page 600 includes a plurality of input fields 602 and606-610 as well as a display area 604. The example web page 600 may beused to solicit donations, for example for a fundraising campaign. Inputfield 602 indicates the webpage for the vendor. As shown in FIG. 6,display area 604 indicates that the user is logged in. Input fields606-610 may each be associated with a different token, wherein eachtoken is associated with a money value. A user wishing to donate aparticular value may select one of the input fields 606-610 tofacilitate a transaction for the displayed amount. In one embodiment,the token generator 122 may generate the tokens such that when one ofthe tokens in input fields 606-610 are selected, the others aredisabled. This may prevent multiple clicks on the same web pageerroneously resulting in multiple charges. In another embodiment, thetoken generator 122 may be configured may be in communication with thebutton generator 123 to assure that the displayed value and the tokenvalue are the same. Similarly, the payment server 140 may be configuredto verify the displayed value versus the requested value.

FIG. 7 shows a transactional diagram for a method for generating a tokenwith a website. The system may be configured to perform an automatedbrowser-initiated payment. In addition to, or alternative to, usinggenerating email tokens, a vendor token generator 122 may also generatetokens for URL based checkout. A browser checkout may be used in ascenario where a customer that is logged in is offered a dollar amountto be paid. Another scenario may be the moment of checkout where a totalis presented to the customer, when the amount is selected by thecustomer a two-click checkout is generated for customer. As shown inFIG. 7 a customer, using a customer device 150 uses a client (e.g. appor web browser) to request a page from vendor server 120 (step 702). Thevendor server 120 generates a token with associated signatures (step704). In submitting the token parameters, the vendor server 120 includesthe IP address of the incoming request and potentially other uniqueidentifying information, such as user agent associated with the browserclient of the customer device 150 or a generated cross-domain cookie.The customer device 150 receives the token (step 706). The customerdevice 150 may then be used to issue a request to the e-commerce system170 (via direct request or JavaScript API call) containing the encryptedpayload. This request may originate from the same system (i.e. customerdevice 150) as the request to the vendor's server 120 originated; theidentifying information (such as the IP address, the user agent, and across-domain cookie value) may also remain part of this request. Thee-commerce system 170 decrypts the payload, and compares the IP address,the user agent and the cross-domain cookie value to the values thepartner's system has independently signed (step 710). If these valuesmatch, the e-commerce system 170 determines that the request isauthorized by the vendor server 120 to make the transaction. Thee-commerce system 170 then performs the transaction as specified by theother values in the token and notifies the vendor server 120 (step 712).

As used herein, the term “processor” broadly refers to and is notlimited to a single- or multi-core processor, a special purposeprocessor, a conventional processor, a Graphics Processing Unit (GPU), adigital signal processor (DSP), a plurality of microprocessors, one ormore microprocessors in association with a DSP core, a controller, amicrocontroller, one or more Application Specific Integrated Circuits(ASICs), one or more Field Programmable Gate Array (FPGA) circuits, anyother type of integrated circuit (IC), a system-on-a-chip (SOC), and/ora state machine.

As used to herein, the term “computer-readable medium” broadly refers toand is not limited to a register, a cache memory, a ROM, a semiconductormemory device (such as a D-RAM, S-RAM, or other RAM), a magnetic mediumsuch as a flash memory, a hard disk, a magneto-optical medium, anoptical medium such as a CD-ROM, a DVDs, or Bluray-Disc, or other typeof device for electronic data storage.

Although the methods and features described above with reference toFIGS. 3-7 are described above as performed using the example system 100of FIG. 1 or system 200 of FIG. 2, the methods and features describedabove may be performed, mutatis mutandis, using any appropriatearchitecture and/or computing environment. Although features andelements are described above in particular combinations, each feature orelement can be used alone or in any combination with or without theother features and elements. For example, each feature or element asdescribed above with reference to FIGS. 1-7 may be used alone withoutthe other features and elements or in various combinations with orwithout other features and elements. Sub-elements of the methods andfeatures described above with reference to FIGS. 1-7 may be performed inany arbitrary order (including concurrently), in any combination orsub-combination.

What is claimed is:
 1. A method for generating tokens for use in anemail-based e-commerce transaction between third party vendor and acustomer that is facilitated by a payment server, the method comprising:generating, by a processor associated with the third party vendor, atoken for use with an email checkout, wherein the token comprises acustomer name, and customer email address; generating, by the processor,an email message for at least one recipient, the email message includinga mailto hyperlink including the token, wherein the mailto hyperlinkgenerates an email response message addressed to the payment serverincluding the token; and receiving, by a receiver, a notification fromthe payment server indicating that the at least one recipient that theemail response message was successfully received by the payment serverand the email-based e-commerce transaction is successful.
 2. The methodof claim 1, wherein the email message comprises multiple tokens.
 3. Themethod of claim 2, wherein each of the multiple tokens is associatedwith a different offered product.
 4. The method of claim 2, wherein eachof the multiple tokens are associated with a different price.
 5. Themethod of claim 1, further comprising generating, by the processor, asecond token for use with an URL checkout, wherein the second token isassociated with the same offered product.
 6. The method of claim 5,further comprising posting the second token on a social media website.7. The method of claim 1, further comprising transmitting a message tothe payment server, indicating tokens that are in use.
 8. A method forgenerating tokens for use in a web-based e-commerce transaction betweenthird party vendor and a customer that is facilitated by a paymentserver, the method comprising: generating, by a processor associatedwith the third party vendor, a token for use with an web checkout,wherein the token comprises a customer name, customer email address, acustomer IP address, at least one browser identifier, and an offeredproduct; generating, by the processor, an email message for at least onerecipient, the email message including a mailto hyperlink including thetoken, wherein the mailto hyperlink generates an email response messageaddressed to the payment server including the token; and receiving, by areceiver, a notification from the payment server indicating that the atleast one recipient that the email response message was successfullyreceived by the payment server, wherein the payment server authenticatesthe transaction based at least in part on the customer IP address andthe at least one browser identifier.
 9. A system for generating tokensfor use in an email-based e-commerce transaction between third partyvendor and a customer that is facilitated by a payment server, thesystem comprising: a processor configured to generate a token for usewith an email checkout, wherein the token comprises a customer name, andcustomer email address; the processor further configured to generate anemail message for at least one recipient, the email message including amailto hyperlink including the token, wherein the mailto hyperlinkgenerates an email response message addressed to the payment serverincluding the token; and a receiver configured to receive a notificationfrom the payment server indicating that the at least one recipient thatthe email response message was successfully received by the paymentserver and the email-based e-commerce transaction is successful.
 10. Thesystem of claim 9, wherein the email message comprises multiple tokens.11. The system of claim 10, wherein each of the multiple tokens isassociated with a different offered product.
 12. The system of claim 10,wherein each of the multiple tokens are associated with a differentprice.
 13. The system of claim 9, wherein the processor is furtherconfigured to generate a second token for use with an URL checkout,wherein the second token is associated with the same offered product.14. The system of claim 13, wherein the processor is further configuredto post the second token on a social media website.
 15. The system ofclaim 9, wherein the processor is further configured to transmit amessage to the payment server, indicating tokens that are in use.